Determining languages for a multilingual interface

ABSTRACT

In some examples, a merchant device at a point of sale (POS) location may present information to a merchant in a first language preferred by the merchant, and may present information to a buyer in a second language preferred by the buyer. The merchant device may switch between the different languages in response to detecting a change in the physical orientation of a display. For instance, in a first orientation in which the display is viewable from a merchant direction, the merchant device may present information in the language preferred by the merchant. When the orientation of the display is changed to a second orientation in which the display is viewable from a buyer direction, the merchant device may present information in the language indicated to be preferred by the buyer. Various techniques may be used for determining the preferred language of a particular buyer.

RELATED APPLICATIONS

This application claims priority to and is a continuation application ofU.S. patent application Ser. No. 15/011,806, filed on Feb. 1, 2016,which claims priority to and is a divisional application of U.S. patentapplication Ser. No. 14/301,603, filed on Jun. 11, 2014, now U.S. Pat.No. 9,324,065, which issued on Apr. 26, 2016, the entire contents ofwhich are incorporated herein by reference.

BACKGROUND

People often conduct transactions in person with merchants for acquiringmany different types of goods and services. However, merchants and/orthe employees of the merchants do not always speak the same language astheir customers. Consequently, it can sometimes be challenging formerchants and customers to communicate information during an in-persontransaction.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features.

FIG. 1 illustrates an example environment for a multilingual paymentservice according to some implementations.

FIG. 2 illustrates an example merchant device for use with amultilingual payment service according to some implementations.

FIGS. 3A-3C illustrate examples of configurations of a merchant deviceable to be used for a multilingual payment service according to someimplementations.

FIG. 4 illustrates an example interface enabling entry of an itemselection according to some implementations.

FIGS. 5A and 5B illustrate example interfaces that may be presented to abuyer according to some implementations.

FIGS. 6A and 6B illustrate example interfaces that may be presented to abuyer according to some implementations.

FIG. 7 illustrates an example environment for controlling access tointerfaces based on the direction that a display is facing according tosome implementations.

FIG. 8 is a flow diagram illustrating an example process for determininglanguage information and for sending language information to a merchantdevice according to some implementations.

FIG. 9 is a flow diagram illustrating an example process for presentinginformation in different languages based on display orientationaccording to some implementations.

FIG. 10 is a flow diagram illustrating an example process forcontrolling access to one or more interfaces based on an orientation ofa display according to some implementations.

FIG. 11 illustrates an example architecture of a system for providing apayment service with multilingual capability according to someimplementations.

FIG. 12 illustrates select components of an example merchant deviceaccording to some implementations.

FIG. 13 illustrates select components of one or more example servicecomputing devices according to some implementations.

FIG. 14 illustrates select components of an example buyer deviceaccording to some implementations.

DETAILED DESCRIPTION

Some implementations described herein include techniques andarrangements for enabling a multilingual transaction between a merchantand a buyer. For instance, a computing device or other merchant deviceat a point of sale (POS) location may present information to a merchantin a first language, and may present information to a buyer in a second,different language. In some cases, the merchant device may switchbetween the different languages in response to detecting a change in thephysical orientation of a display associated with the merchant device.For instance in a first orientation, in which the display is facing adirection associated with the merchant, the merchant device may presentinformation in a first language that is preferred by the merchant. Upondetecting rotation or other change in orientation of the display of themerchant device (e.g., indicating that the display is facing a differentdirection to be viewable by a buyer), the merchant device may presentinformation in a second language indicated to be preferred by the buyer.

In some cases, in addition to, or as an alternative to switching betweenlanguages, the merchant device may control access to certain applicationor device features based on the detected orientation of at least thedisplay of the merchant device. For instance, the merchant device maypresent a first user interface (UI) on a touchscreen display. The firstUI may include one or more virtual controls for enabling entry ofinformation for a transaction, such as for enabling the merchant toselect one or more items that a buyer desires to purchase. When themerchant has completed entry of information related to the transaction,the merchant device may present a second UI intended for presentation tothe buyer. For instance, the second UI may include one or more virtualcontrols to enable the buyer to enter information or otherwise performactions toward completion of the transaction. In some examples, thesecond UI may be presented on the display before the merchant rotates orotherwise changes the position of the display to face the buyer. Inother examples, the second UI may be presented on the display inresponse to the merchant device detecting rotation or other change inthe position of the display. In either event, the merchant devicereceives an indication of a change in the physical orientation of thedisplay, e.g., movement of the display from a first orientation,viewable by the merchant, to a second orientation, viewable by a buyer.

The merchant device may present the second UI on the display, and thebuyer may interact with the second UI. As several examples, the buyermay enter a signature for a payment card, enter an amount for a tip,enter contact information for receiving a receipt, enter other types ofbuyer information, e.g., in response to a question, or enter other typesof information for enabling completion of the transaction. Thus, thesecond UI may enable touch-based entry of information by the buyer forcompleting the buyer's stage of the transaction. When the buyer hascompleted interaction with the second UI, the display may be reorientedback to face the merchant. Based at least in part on the change inorientation of the display from the second orientation back to the firstorientation, the merchant device may enable initiation of a newtransaction by the merchant. In other words, when the display is facingthe direction associated with the buyer, only the buyer UI is presented,and the buyer is unable to access the merchant interface, and is therebyunable to initiate a new transaction, or perform other actions that areproperly performed only by the merchant. Subsequently, when the merchantdevice detects that the display has been returned to the firstorientation, i.e., facing the direction associated with the merchant,the merchant is able to initiate a new transaction or perform otherfunctions on the merchant device that buyers may be restricted fromperforming.

In some examples, in response to detecting the change in displayorientation from the second orientation back to the first orientation,the merchant device may automatically present another interface on thedisplay that enables the merchant to begin a new transaction.Alternatively, as another example, in response to detecting the changein display orientation from the second orientation to the firstorientation, the merchant device may enable certain virtual controls,such as one or more touchscreen virtual buttons or icons that wereinactive in the second orientation, but which are able to be selectablein the first orientation. For instance, a “start new transaction” buttonmay be able to be selected by the merchant in the first orientation,whereas if the buyer had attempted to select the “start new transaction”button while the display was in the second orientation, the merchantdevice may ignore the attempted selection based on a determination thatthe display is in the second orientation.

As used herein, a merchant may include any business or other entityengaged in offering goods or services for acquisition by buyers inexchange for compensation received from the buyers. Actions attributedto a merchant herein may include actions performed by employees or otheragents of the merchant and, thus, no distinction is made herein betweenmerchants and their employees unless specifically discussed. Inaddition, as used herein, a buyer may include any entity that acquiresgoods or services from a merchant, such as by purchasing, renting,leasing, borrowing, licensing, or the like. Buyers may include customersand/or potential customers of a merchant. Hereinafter, goods and/orservices offered by merchants may be referred to as items. Thus, amerchant and a buyer may interact with each other to conduct atransaction in which the buyer acquires one or more items from amerchant, and in return, the buyer provides payment to the merchant.Accordingly, as used herein, a transaction, such as a POS transaction,may include a financial transaction between a buyer and a merchant forthe acquisition of one or more items, such as at a POS location.

In some examples, a service provider may provide language informationabout a particular buyer to a merchant. For instance, the serviceprovider may provide a payment service to the merchant, and may providethe language information in association with providing the paymentservice. The payment service provided by the service provider mayinclude the provision of software, hardware and/or payment processingservices to the merchant to enable the merchant to receive payments frombuyers and to otherwise conduct POS transactions with buyers.

The service provider may provide the payment service to a large numberof merchants, and as a result, the service provider may receive POStransaction information for a large number of POS transactions that areconducted between buyers and merchants at a plurality of respective POSlocations for a variety of items. The service provider may organize thereceived transaction information into respective merchant profiles andbuyer profiles associated with the respective merchants and buyersparticipating in the respective POS transactions. Thus, the serviceprovider may associate the transaction information for specifictransactions with respective buyer profiles associated with respectivebuyers who conducted the transactions. A buyer profile associated with aparticular buyer may contain buyer identifying information thatindicates information about the buyer, and item purchase informationthat indicates details of items purchased, amount paid, time and placeof the transaction, and so forth.

In some examples, based on the information included in the buyerprofiles, the service provider may be able to determine a preferredlanguage of a particular buyer and can associate the preferred languagewith the buyer profile of that buyer. For instance, when paying for aPOS transaction, a buyer may provide the payment that is due to amerchant using any of cash, a check, a payment card, or an electronicpayment account, such as may be accessed using a buyer device carried bythe buyer. During the POS transaction, the merchant device can send, tothe service provider, payment information in addition to othertransaction information, such as a description of the items selected bythe buyer, prices of the items selected, a time, place and date of thetransaction, and so forth. In addition, the merchant device can ofteninclude buyer identifying information with the transaction informationsent to the service provider. For instance, buyer identifyinginformation may be determined from a payment card of the buyer, from anelectronic payment account of the buyer, from a merchant club membershipor other incentive program for which the buyer has signed up, or thelike. As one example, the merchant may send payment card information ofa buyer to the service provider to obtain authorization for transactionsbeing conducted using the payment card as the payment instrument.

Based on the buyer identifying information, the service provider mayidentify a particular buyer profile corresponding to the buyerinformation received for the current transaction. If a particularlanguage has already been associated with the particular buyer profile,the service provider may send at least an indication of the particularlanguage to the merchant device prior to completion of the currenttransaction. For example, the language information may be sent to themerchant device while the merchant device is waiting for credit cardauthorization or other payment authorization from the service provider.The merchant device may then use the language information to determinethe language to present on the display to be viewed by the particularbuyer.

Furthermore, in some examples, merchant profiles may also indicate alanguage preferred by a particular merchant or by particular employeesof a particular merchant. As an example, suppose that a particularmerchant logs in to an associated merchant device, and has previouslyindicated that Spanish is a preferred language. Accordingly, themerchant UI may be presented in Spanish to the particular merchant.Next, suppose that a buyer wishes to purchase an item from theparticular merchant and provides a payment card to the merchant as apayment instrument. The merchant may swipe the payment card, and thecard information may thereby be sent to the service provider. Based onthe payment card information, the service provider may identify a buyerprofile associated with the current buyer, and may further determine apreferred language of the current buyer, such as may have beenpreviously associated with the buyer profile. Suppose that the preferredlanguage associated with the buyer profile in this example is Japanese.The service provider may send, to the merchant device, a communicationthat indicates Japanese is the preferred language of the current buyer.In response, the merchant device may present the buyer UI in Japanesewhen the display of the merchant device is oriented toward the currentbuyer, and may present the buyer UI in Spanish, i.e., the languagepreferred by the merchant, when the display is oriented toward themerchant.

Various techniques may be used by the service provider for determining alanguage to associate with a buyer profile of a particular buyer. As oneexample, the buyer may expressly specify a preferred language such aswhen signing up for an electronic payment account with the paymentservice of the service provider. For example, as discussed additionallybelow, the buyer may be able to pay for transactions using an electronicpayment account accessible through a buyer application installed on abuyer device, such as a smart phone, a wearable computing device, orother portable computing device carried by the buyer. Accordingly, whenthe buyer signs up for an account with the payment service, the buyermay provide an express indication of a preferred language, and thepreferred language is then associated with the buyer profile of theparticular buyer.

As another example, a merchant device may be configured make a query tothe buyer, such as during a transaction. For example, when the merchantorients the display of the merchant device to face the buyer, iflanguage information has not yet been associated with the buyer profileof the particular buyer, the buyer interface presented to the buyer mayask the buyer to select a preferred language. The selected preferredlanguage may be associated with the profile of the current buyer.Subsequently, during future transactions, it is not necessary to ask thebuyer to again select a preferred language, as the language informationmay be obtained from the buyer profile.

As still another example, the service provider may determine implicitlya preferred language of the particular buyer, such as from actions ofthe buyer or from other information obtained about the buyer. Forexample, suppose that the buyer provides an email address for receivingreceipts for transactions. Furthermore, suppose that when the buyeraccesses the email receipts, the buyer uses a browser that is set to aparticular language, such as German. For instance, the browser localemay have been set to Germany or the user may have otherwise indicatedGerman as a preferred language to the browser. As one example, an HTTP(hypertext transfer protocol) accept-language header received by theservice provider when the buyer uses the browser to access the receiptsmay indicate the language preferred by the buyer. Accordingly, based onthe buyer accessing the email receipts primarily using a web browserthat is set to the German language, this language may be implicitlyassociated with the buyer profile as a preferred language of theparticular buyer. Numerous other techniques for determining a preferredlanguage of a particular buyer will be apparent to those of skill in theart having the benefit of this disclosure.

In addition, various techniques may be used for determining theorientation of the display of the merchant device, such as whether thedisplay is currently viewable by the merchant or by the buyer. As oneexample, when the display is mounted on a stand, rotation or otherrepositioning of the display may be detected by a switch included in thestand. Additionally or alternatively, the merchant device may includeone or more sensors such as an accelerometer, gyroscope, compass, or thelike, that can detect when the orientation of the display has beenchanged from a first orientation to a second orientation. Furthermore,in some examples, facial recognition, body recognition, environmentrecognition, audio recognition, and/or biometric sensing, such asfingerprint scanning, may be used for determining whether the display iscurrently facing the merchant or the buyer. For example, the merchantdevice may include a camera associated with the display and the merchantdevice may be trained to recognize the two different orientations basedon input from the camera. As one example, when a wall-mounted menu isdetectable in the background, the display may be facing the merchant,whereas when a door to the store is detectable in the background, thedisplay may be facing a buyer. As still another example, the merchantdevice may include a control that the merchant may select prior toreorienting the display to switch between the language preferred by themerchant and the language preferred by the buyer.

For discussion purposes, some example implementations are described inthe environment of a merchant device that is used in conjunction with apayment service for conducting POS transactions. However,implementations herein are not limited to the particular examplesprovided, and may be extended to other environments, other systemarchitectures, other applications, and so forth, as will be apparent tothose of skill in the art in light of the disclosure herein.

FIG. 1 illustrates an example environment 100 for a payment service anda language information service according to some implementations. Forinstance, the environment 100 may enable a service provider 102 toprovide a payment service in which merchants are able to conduct POStransactions with a plurality of buyers, such as for selling items tothe buyers. Further, the environment 100 may enable the service provider102 to provide language information to assist the merchants indetermining a language that may be preferred by a customer during a POStransaction. Examples of various different languages that may be used insome implementations herein may include English, Spanish, Japanese,French, Tagalog, Mandarin, Hindi, Korean, German, Portuguese, Russian,Arabic, Bengali, Punjabi, Vietnamese, Dutch, Italian, Swedish,Norwegian, Danish, Finnish, and Hebrew, to name a few. Further, in someexamples one dialect of a particular language may be a first language,while another dialect of the particular language may be a secondlanguage.

In the illustrated example, a merchant device 104 is able to communicateover one or more networks 106 with one or more service computing devices108 of the service provider 102. Further, the merchant device 104 may beassociated with a merchant 110. Additionally, in some examples, aplurality of other merchant devices (not shown in FIG. 1) may beassociated with a plurality of other merchants who may also participatein the payment service provided by the service provider 102. Themerchant device 104 may include an instance of a merchant application112 that executes on the merchant device 104. The merchant application112 may provide POS functionality to the merchant device 104 to enablethe merchant 110 to accept payments from one or more buyers 114 at a POSlocation 116. For example, the merchant 110 may use the merchant device104 to accept payments from various different types of paymentinstruments, e.g., payment cards, electronic payment, cash or check, atthe POS location 116 from the one or more buyers 114.

In some types of businesses, the POS location 116 may correspond to astore or other place of business of the merchant 110, and thus, may be afixed location that typically does not change on a day-to-day basis. Inother types of businesses, however, the POS location 116 may change fromtime to time, such as in the case that the merchant 110 operates a foodtruck, is a street vendor, a cab driver, or has an otherwise mobilebusiness, e.g., in the case of merchants who sell items at buyers'homes, buyers' places of business, and so forth.

Further, the physical orientation of the merchant device 104 may bechanged during a transaction. For instance, the change in physicalorientation may cause the merchant application 112 executing on themerchant device 104 to switch between a first language that is preferredby the merchant 110, and a second language that has been indicated to bepreferred by a particular buyer 114 participating in the currenttransaction. Additionally, or alternatively, the physical orientation ofthe merchant device 104, i.e., the direction that the electronic displayscreen of the merchant device 104 is currently facing, may be used tocontrol which features of the merchant application 112 are accessible onthe merchant device 104.

In some examples, the buyer 114 may have a buyer device 118 that canexecute a buyer application 120. For instance, some buyers 114 may carrybuyer devices 118, such as smart phones, tablet computers, wearablecomputing devices, or the like, as further enumerated elsewhere herein,and some of these buyer devices 118 may have installed thereon the buyerapplication 120. The buyer application 120 may include electronicpayment capability, which enables the buyer 114 to make a payment to themerchant 110 using the buyer application 120, rather than paying with aphysical payment card, cash, check, etc.

The buyer application 120 may further enable the buyer 114 to check inwith the particular merchant 110, e.g., at the merchant's store or priorto entering the merchant's store, such as when the buyer is within acertain distance from the merchant device 104, the merchant's address,etc. For example, the buyer 114 may check in with the merchant 110 toplace an order for an item 122. As one example, the buyer 114 may beable to place the order for the item 122 through the buyer application120, may skip waiting in a line for ordering items, may pay for thetransaction using the buyer application 120, and may proceed directly toan area of the merchant's store to pick up the ordered item 122. Throughcommunication with the service computing device 108, or through directcommunications between the buyer device 118 and the merchant device 104,the buyer's order may be automatically provided to the merchant device104.

Regardless of the type of payment instrument used, the merchant 110 andthe buyer 114 may conduct a transaction by which the buyer 114 acquiresthe item 122 from the merchant 110 at the POS location 116. The merchantapplication 112 on the merchant device 104 may send transactioninformation 124 to the service computing device 108, e.g., while thetransaction is being conducted at the POS location 116. In otherexamples, such as if the merchant device 104 is processing transactionsoffline, the transaction information 124 may be sent in a batch at asubsequent point in time or using other suitable techniques.

The transaction information 124 may include information regarding thetime, place, and the amount of each respective transaction, informationrelated to the item 122 acquired, a type of payment being used (e.g.,cash, check, payment card, electronic payment), as well as additionalinformation, such as buyer identifying information. For instance if apayment card 126, such as a credit card, debit card, charge card,prepaid card, or the like, is used as a payment instrument, thetransaction information 124 can include data stored in the payment card,e.g., Track 1 data (cardholder name, card number and other cardinformation). In addition, when completing the transaction, a buyer 114may sometimes provide an email address for receiving a receipt throughemail, a phone number for receiving a receipt via text message, or thelike. Other examples of transaction information 124 that can be capturedinclude item purchase information, such as detailed item information,e.g., an itemized listing of the items being acquired, the price beingpaid for each item, descriptors of the items (size, flavor, color,etc.), geolocation data indicating a geographic POS location of aparticular transaction, online/offline card data, data describing themerchant 110 and/or the merchant device 104, e.g., a merchantidentifier, a merchant category code (MCC), or the like. Additionally,in some examples the transaction information 124 may include any type ofdata that is received upon a buyer's authentication into a socialnetwork, if any, buyer identification information obtained from amerchant club card, points program, or other incentive programs, andvarious other types of information, as discussed additionally below.

The service computing device 108 may also receive transactioninformation from a plurality of other merchant devices (not shown inFIG. 1) associated with a plurality of other merchants. For example, alarge number of other merchants may also operate their own merchantdevices for conducting transactions via the payment service.Accordingly, the transaction information from the merchant devicesassociated with the other merchants may also be received by the servicecomputing device 108.

The service computing device 108 may receive the transaction information124 and may associate the transaction information 124 with merchantinformation 128 maintained by the service computing device 108. Forexample, the transaction information 124 may be associated with aparticular merchant profile 130 corresponding to the merchant 110. Thus,the service provider 102 may maintain a plurality of merchant profiles130, such that each merchant registered with the payment service may beassociated with a respective merchant profile 130 that includestransaction information for transactions conducted by that merchant withone or more associated merchant devices.

In addition, the service computing device may extract buyer information132 from the transaction information 124. Based in part on the buyerinformation, the service provider may associate transaction information124 for a particular transaction with a respective buyer profile 134 ofa plurality of buyer profiles 134 maintained by the service provider102. For example, if a payment card 126 is used as the paymentinstrument, the transaction information 124 for a particular transactionmay include a payment card identifier of the payment card 126, and mayfurther include the name of the holder of the payment card 126.Accordingly, a particular buyer profile 134 may be associated with anidentifier of the payment card 126 and/or the name corresponding to theholder of the payment card. Additional transaction information from theparticular transaction may be related to this buyer profile, such as thePOS location of the transaction, the amount of the transaction, the timeand date of the transaction, the items acquired through the transaction,descriptive information about the items acquired, the price paid for theitems, and so forth.

In some examples, the service computing device 108 may include alanguage determination module 136 that examines the data in the buyerprofiles 134 and/or the merchant profiles 130 to determine one or morelanguages to be used by a particular merchant device 104 during aparticular transaction. For example, the language determination module136 may receive transaction information 124 for a current transaction,and, in response may send language information 138 to the merchantdevice 104 while the transaction is still ongoing. As one example, thelanguage information 138 may indicate a preferred language associatedwith a particular buyer profile corresponding to the buyer conductingthe current transaction. As another example, if there is no preferredlanguage associated with the particular buyer profile, the languageinformation 138 may indicate this and, in some examples, may furtherinclude an instruction that causes the merchant device 104 to display ascreen to the buyer that requests the buyer select a preferred language.Alternatively, the language selection screen may be displayed to themerchant, who may verbally request the preferred language from thebuyer.

Additionally, or alternatively, the merchant application 112 may includea language module 140 that may determine a language to present atvarious stages of a transaction, either independently, or based on thelanguage information 138 that may have been received from the servicecomputing device 108. As one example, a plurality of user interfacescreens or other components in various different languages may beprovided to the merchant device 104 preconfigured in the variousdifferent languages as part of the merchant application 112. As anotherexample, the user interfaces may be translated to other languages asneeded by the language module 140.

As one example, suppose that a merchant 110 (or a particular employee ofthe merchant) prefers a first language, such as French. However, supposethat the merchant 110 performs transactions at a point-of-sale location116 where most of the customers of the merchant prefer a secondlanguage, such as English. Accordingly, the merchant 110 may configure alanguage preference in a merchant profile to indicate that the preferredlanguage of the merchant is French. At least a portion of the merchantprofile may be stored locally on the merchant device 104 as well as atthe service computing device 108.

When the merchant 110 logs in to the merchant device, the languagemodule 140 may determine the preferred language of the merchant 110 as aresult, user interfaces that are presented to the merchant 110 arepresented in the first language, e.g., French, while the user interfacesthat are presented to the buyers 114 are automatically presented in thesecond language, i.e., English, by default. For instance, when themerchant device 104 detects a change in the orientation of the merchantdevice 104, which may be indicative that an interface is being presentedto the buyer 114, the interface may be presented in the defaultlanguage. This implementation may be employed regardless of whether themerchant device 104 is operating in an offline or online mode.Additionally, in some examples, the language determination module 136and/or the language module 140 can use demographics of a particular POSlocation for setting a default language to be used by the merchantdevice 104. Furthermore, different employees of the merchant may havedifferent language preferences set, such that when a particular employeelogs in, the language preference of that employee may be used during thesession during which the employee is logged in.

In the example of FIG. 1, the merchant device 104 includes a display 142that may present information to the merchant 110 when positioned in afirst orientation 144 and to the buyer 114 when positioned in a secondorientation 146. In some examples, the display 142 may be a touchscreendisplay able to receive touch-based user inputs, although other types ofdisplays and input devices may be used in other examples. As oneexample, the display 142 may be part of a tablet computing device orotherwise associated with a computing device that executes the merchantapplication 112 to provide the functionality of the merchant device 112.

In the illustrated example, a support 148 is configured to support thedisplay 142 in the first orientation 144, e.g., facing a firstdirection, and may be positioned to the second orientation 146, e.g.,facing a second direction generally away from the first direction. Forinstance, in the first orientation 144, the display 142 may not beeasily visible to a buyer standing on a buyer side of the merchantdevice, whereas when the display 142 is repositioned to face the buyerin the second orientation 146, the display 142 may not be easily visibleto the merchant located on the merchant side of the merchant device.

As one example, the support 148 may be a stand of plastic, metal orother suitable material that includes a swivel base 150 that allows thesupport 148 and the display 142 to be pivoted around a vertical pivotaxis 152, as indicated by arrow 154. In some examples, the rotation ofthe support on the base 150 may be performed manually by the merchant110 or the buyer 114. In other examples, the rotation may be automated,such as by a motor (not shown in FIG. 1), and controlled by the merchantapplication 112, or by a control controlled manually by the merchant.Thus, regardless of the source of motivation, the merchant device 104may rotated around the pivot axis 152 to reposition the display 142between the first orientation 144 and the second orientation 146.

One or more of various different types of sensors may be used to provideorientation information 156 to the merchant application 112. Theorientation information 156 may indicate a change between the firstorientation 144 and the second orientation 146. As one example, a switch158 may be associated with the base 150 for detecting relative motionbetween the support 148 and the base 150. Accordingly, rotating themerchant device 104 from the first orientation 144 to the secondorientation 146 may actuate the switch 158. The switch 158 may send, asthe orientation information 156, a signal to a processor (not shown inFIG. 1) of the merchant device 104 to provide an indication that atleast the display 142 has been rotated from the first orientation 144 tothe second orientation 146. Any suitable type of switch may be used,such as mechanical, electromechanical, electronic, etc.

As one example, information 160(1) may be presented on the display 142when the display 142 is in the first orientation 144. For instance, theinformation 160(1) may be presented in a first language. The support 148and the display 142 may be rotated to the second orientation 146, whichmay trip or otherwise actuate the switch 158. In response to theorientation information 156 from the switch 158, the merchantapplication 112 may present information 160(2) on the display 142 whenthe display 142 is in the second orientation 146. As one example, theinformation 160(2) may be a translated version of the information 160(1)in the second language. As another example, the information 160(2) maybe different information written in the second language that is intendedfor viewing and/or interaction by the buyer. When the display 142 andsupport 148 are rotated back to the first orientation 144, the switch158 may be actuated again, or may otherwise provide an indication thatthe display 142 has returned to the first orientation 144. In response,the information 160(1) may be again presented in the first language, ordifferent information presented on the display 142 may be presented inthe first language.

Additionally, or alternatively, numerous other types of sensors (notshown in FIG. 1) may be used for determining a change in the orientationof the display 142. For example, the merchant device 104 may includeonboard sensors such as an accelerometer, a compass, a gyroscope, aproximity sensor, or the like, which may detect a change in theorientation of the display 142. As one particular example, the merchantdevice 104 may include a tablet computing device that provides thedisplay 142 and the sensors, and which is mounted on the support 148.Additionally, or alternatively, one or more sensors may be included inthe support 148. Accordingly, the sensors of the merchant device 104 maydetect a change in orientation of at least the display 142, and mayprovide sensor information as the orientation information 156 to themerchant application 112. In response, the merchant application 112 maypresent the information 160(2) on the display 142 to the buyer 114 inthe second language based on the change in the orientation of thedisplay 142 to the second orientation 146.

As another example, the merchant device 104 may include a camera (notshown in FIG. 1) associated with the display 142. The merchant 110 maytrain the merchant device 104 to recognize the two differentorientations 144 and 146 based on input from the camera. For instance,the merchant application 112 may include a training and recognitionfeature that enables the merchant 110 to train the merchant application112 to recognize the merchant 110 and/or the surrounding environment toenable the merchant application 112 to recognize a current orientationof the display 142. For example, a current image received from thecamera may serve at least in part as orientation information 156, toindicate a current direction that the display 142 is facing. Thus, themerchant application 112 may use facial recognition, body recognition,environment recognition, or the like, to recognize the currentorientation of the display 142.

Additionally, or alternatively, the merchant application 112 may useaudio recognition and/or biometric sensing to distinguish the merchant110 from buyers 114. For example, a microphone of the merchant device104 may enable voice recognition such that the merchant 110 may providea voice command when the display is oriented for viewing by themerchant. For instance, the voice command may cause the merchantapplication 112 to initiate a new transaction.

As another example, the merchant device may include a fingerprint sensoror other biometric sensor that the merchant is able to touch when thedisplay is oriented for viewing by the merchant. For instance, themerchant may have previously provided authentication information forassociating a fingerprint with the merchant device 104. Thus, themerchant 110 may touch the fingerprint sensor to initiate a newtransaction, whereas if a buyer were to touch the fingerprint sensor,the input may be ignored, as the fingerprint is not recognized.

As another alternative, the merchant device 104 may include a physicalbutton or other control that is not rotated with the display 142, andthat the merchant 110 may select when the display 142 is rotated back tothe face the merchant. For instance, selection of the physical controlmay indicate to the merchant application that display 142 is orientedtoward the merchant. Thus, the merchant application may display tointerfaces in the first language of the merchant, and furthermore whenorientation is used for access control, and access is permitted tomerchant interfaces e.g., for initiating a new transaction, forcancelling a transaction, for changing merchant application settings,etc. Furthermore, while several examples have been provided, numerousother techniques for detecting a change in the orientation of thedisplay 142 and/or the merchant device 104 will be apparent to those ofskill in the art having the benefit of the disclosure herein.

In some instances, the merchant 110 can interact with the merchantdevice 104 to specify a language preferred by the merchant 110 whenusing the merchant device 104. For example, each employee of themerchant 110 may be able to specify a preferred language, and uponlogging in to the merchant device 104, the merchant application 112 maypresent merchant interfaces in the preferred language. Thus, themerchant application 112 may present one or more UIs (not shown inFIG. 1) to the merchant 110 in a preferred language. Additionally, insome examples, the preferred language of the merchant may be inferred,such as based on a language that the merchant 110 uses when signing upfor the payment service. In either event, the preferred language of amerchant or particular merchant employee may be associated with therespective merchant profile 130, at least part of which, as mentionedabove, may be stored locally on the merchant device 104 such as toenable multi-language functionality when the merchant device 104 is inan off-line mode.

As one example, suppose that the merchant 110 prefers English and haspreviously indicated this preference to the language module 140 on themerchant device 104. Accordingly, when the merchant 110 is logged in tothe merchant device 104, the language module 140 may cause the merchantapplication 112 to present information 160(1) to the merchant 110 inEnglish. Suppose that the buyer 114 has selected the item 122 forpurchase and wishes to pay with an electronic payment account throughthe buyer application 120. The buyer 114 may check in with the merchantdevice 104 via the buyer application 120. The merchant device 104 and orthe buyer device 118 may send transaction information 124 to the servicecomputing device 108. The service computing device 108 may determine aparticular buyer profile 134 that corresponds to the particular buyer114 and/or buyer device 118. The language determination module 136 mayinform the merchant device 104 of the preferred language associated withthe particular buyer profile 134 by sending the language information 136to the merchant device 104. For example, the language information 136may include at least the name or other identifier of the preferredlanguage.

The language module 140 of the merchant application 112 may use thelanguage information 136 to determine the language of the UIs to bepresented to the buyer 114. For example, the merchant 110 may rotate themerchant device 104 so that the display 142 is in the second orientation146, such as to enable the buyer 114 to sign or otherwise authorize thetransaction for the item 122. Based on the language information 138received from the service computing device 108, the merchant application112 may present the information 160(2) in the language indicated in thebuyer profile 134 to be preferred by the particular buyer. Followingcompletion of the buyer stage of the transaction, the merchant devicemay be rotated back so that the display 142 again faces the merchant110. Based on the language previously indicated to be preferred by themerchant 110, the merchant device 104 may present the information 160(1)in the language preferred by the merchant 110, which may be anindication that the transaction has been successfully completed.

As another example, if the buyer 114 instead chooses to pay with apayment card 126, the merchant 110 may enter the buyer's selection ofitem 122 into the merchant device 104 using a merchant UI as discussedadditionally below. The merchant 110 may enter information for thetransaction and request the payment card 126 from the buyer 114. Themerchant 110 may swipe the payment card 126 in a card reader 162, whichmay be included with or associated with the merchant device 104, such aslocated in the stand 148. Payment card information, such as card number,card holder name, and other information about the transaction may besent to the service computing device 108 as the transaction information124. The service computing device 108 may match the card informationwith one of the buyer profiles 134, and may determine a preferredlanguage associated with the identified buyer profile 134. The languagedetermination module 136 may send the preferred language as the languageinformation 138 to the merchant device 104, which may use the preferredlanguage when presenting the information 160(2) to the buyer 114 asdiscussed above. Alternatively, if there is no preferred languageassociated with the particular buyer profile 134, the languagedetermination module 136 may send, as the language information 138, acommunication indicating that there is no preferred language and aninstruction for the merchant device to request a preferred language fromthe particular buyer.

FIG. 2 illustrates an example of the merchant device 104 including anexample merchant user interface for enabling a POS transaction between amerchant and a buyer according to some implementations. In this example,the merchant device 104 includes the stand 148, which supports thedisplay 142 on the swivel base 150 to enable the display 142 to berotated between a first orientation viewable by the merchant (not shownin FIG. 2) and a second orientation viewable by the buyer 114, asdiscussed above. The merchant device 104 further includes a frame 202for holding the display 142 on the support 148 and a camera 204 that maybe used for orientation recognition in some examples, as discussedabove.

In this example, the merchant device 104 may present a first UI 206 tothe merchant in a language preferred by the merchant. The first UI 206may enable the merchant to enter one or more selections of the buyer 114and determine an amount of payment due for the one or more selecteditems. For instance, the first UI 206 may include a plurality of iconsother representations 208 of items that are offered by the merchant. Inthe case that the display 142 is a touchscreen, the merchant may enterselections such as by tapping on a representation 208 of a particularitem selected by the buyer 114. The UI 206 may further include aselected items area 210 that indicates the items selected by the buyer114 and a total amount of payment due for the transaction. Variousportions of the UI 206 may include text 212, such as for descriptions ofthe items or for providing other information to the merchant. This text212 may be presented in the language determined to be preferred by themerchant. When all the items selected by the buyer have been enteredinto the UI 206, the merchant may request a payment instrument from thebuyer 114.

As mentioned above, the buyer 114 may use any of a variety of differentpayment instruments when participating in a POS transaction. Forexample, the buyer 114 may typically have a plurality of payment cards126, such as credit cards, debit cards, prepaid cards, and so forth,which the buyer 114 may use for making payment. Furthermore, in additionto payment cards, a buyer 114 may carry a buyer device 118, as discussedabove, which may include the buyer application 120. For example, thebuyer application 120 may include an electronic payment module 214 thatuses an electronic payment account of the buyer 114 for makingelectronic payments for transactions. In some cases, the electronicpayment account of the buyer 114 may be linked to one of the buyer'spayment cards, such as a credit card. Accordingly, the buyer application120 may enable the buyer 114 to pay for a transaction with the linkedcredit card without having to produce the credit card, thereby enablinga card-less payment to the merchant with the credit card. As mentionedabove, the buyer application 120 and the corresponding electronicpayment account may be associated with a particular buyer profile thatmay include various buyer information including, for example, thebuyer's name, information describing the payment card linked to theelectronic payment account, and an email address linked to theelectronic payment account to which receipts can be sent for electronicpayment transactions that are conducted by the buyer 114 using the buyerapplication 120. Further, the particular buyer profile may indicate apreferred language of the particular buyer. For instance, the buyer mayhave indicated the preferred language when signing up for the electronicpayment account, or when updating preferences for the electronic paymentaccount, or the preferred language may have been determined by any ofthe other techniques described herein.

In addition to the above-discussed payment instruments, the buyer 114may also optionally pay with a check 216 or cash 218. For example, ifthe buyer 114 pays with check 216 or cash 218, the merchant maysometimes also receive an identifier that provides additionalidentification information about the buyer 114. For instance, a merchantmay have a club card, a points program, or other incentive program thatenables identification of the buyer 114 to the merchant and thereby tothe merchant application 112. As an example, as part of the merchant'sincentive program, the buyer 114 may provide a telephone number, emailaddress, club card, etc., and this buyer identifying information may becross-referenced to associate a particular transaction with a particularbuyer profile for determining a preferred language of the buyer if apreferred language has been associated with the buyer profile.Alternatively, if the buyer 114 pays with a check, the buyer 114 may berequired by the merchant to provide buyer information in associationwith the check, which may include checking account number, telephonenumber, residential address, and other identification information.Accordingly, this information may also be associated with the particulartransaction, and may thereby enable the transaction to be associatedwith a buyer profile. Thus, despite the different possible paymentinstruments that may be used, the service provider may often be able toassociate a particular buyer with a buyer profile for that buyer andthereby determine whether a preferred language has been associated withthe particular buyer.

FIGS. 3A-3C illustrate several alternative examples of configurations ofthe merchant device according to some implementations. In FIG. 3A, theportion of the merchant device including the display 142 is mounted on asupport 302 that includes a first card reader 162(1) and a second cardreader 162(2). Furthermore, in this example, the support 302 includes apivot axis 304 that enables the display 142 to be rotated about ahorizontal pivot axis, as indicated by the arrow 306, rather than avertical pivot axis as in the example of FIG. 1. Accordingly, thedisplay 142 may be flipped about the horizontal pivot axis 304 betweenthe first orientation 144 in which the display is facing a firstdirection e.g., toward the merchant, and the second orientation 146 inwhich the display is facing a second direction, e.g., away from themerchant and toward the buyer.

FIG. 3B illustrates another example of the merchant device 104 that doesnot include a support. In this example, the merchant device 104 isself-contained in a tablet computing device, smart phone, or otherportable computing device that includes the display 142. A card reader308 may be attached to the merchant device 104 such as by plugging intoone or more ports of the merchant device 104. As one particular example,the card reader 308 may plug in to a microphone jack of the merchantdevice 104, and payment card information may be delivered by the cardreader 308 to the merchant device 104 through the microphone jack. Inthe example of FIG. 3B, the merchant 110 may complete the merchant stageof the transaction such as by entering item information, and swiping thepayment card of the buyer.

When the merchant application presents a buyer interface on the display142, such as to enable the buyer to enter a signature for the paymentcard, the merchant may hand the merchant device 104 to the buyer toenable the buyer to entered the quest of information such as signature,receipt information etc. In response to the merchant handing themerchant device 104 to the buyer, the merchant device may detect achange in orientation based on orientation information receive one ormore sensors on board the merchant device as discussed above, and makedetermine that the merchant device is now in the second orientation 146.For example, because the transaction has reached a point at which thebuyer will be expected to make input, the merchant device 104 may beconfigured to determine that a handoff will soon occur, and may use oneor more recognition algorithms for detecting input from one or moresensors that indicate the merchant device 104 has been handed to thebuyer 114, and therefore the display is viewable from a differentdirection.

In response, to the handing of the merchant device 104 to the buyer 114,the merchant device 104 may present the buyer user interface in thelanguage preferred by the buyer 114. When the buyer 114 has completedthe buyer stage of the transaction, the buyer 114 may hand the merchantdevice 104 back to the merchant 110. In response to detecting that theorientation of the display 142 has returned to the first orientation144, e.g., is facing a direction that is associated with the merchant,the merchant device 104 may present information in the languagepreferred by the merchant 110.

FIG. 3C illustrates another example of the merchant device 104 in whichthere is a first display 142(1) that is oriented facing in a directionassociated with the merchant 110, and a second display 142(2) that isoriented facing in a direction associated with the buyer 114. In thisexample, rather than detecting a change in orientation the display, themerchant device 104 presents the information on the first display 142(1)in the language preferred by the merchant, and presents the informationon the second display 142(2) in the language preferred by the particularbuyer 114. For example, during the merchant stage of the transaction thebuyer may be presented with an indication of the items selected andprice, but may otherwise not be able to view the merchant interfacepresented on the first display 142(1). Thus, the information presentedto the buyer may be in the buyer's preferred language, if known at thisstage, such as if the buyer has checked in with the merchant, while theinformation presented to the merchant is presented in the merchant'spreferred language. Subsequently, in response to receiving languageinformation indicating the preferred language of the buyer, theinterfaces presented to the buyer during the buyer stage of thetransaction may be presented on the second display 142(2) in thepreferred language of the buyer, while the interfaces presented to thebuyer may be presented to the merchant on the first display 142(1) inthe preferred language of the merchant. Furthermore, while severalexample configurations of merchant devices 104 have been described fordiscussion purposes, numerous other configurations will be apparent tothose of skill in the art having the benefit of the disclosure herein.

FIG. 4 illustrates an enlarged view of the example user interface 206discussed above with respect to FIG. 2 according to someimplementations. For example, some types of transactions may include amerchant stage and a buyer stage. During the merchant stage, themerchant may be presented with the UI 206 or other suitable interface toenable the merchant to enter item information for one or more itemselected for purchase by the buyer. In addition, in some examples,during the merchant stage, the merchant may receive a payment card ofthe buyer and may swipe the payment card in a card reader as describedabove. Alternatively, in some examples, the merchant may receive otheridentifying information of the buyer during the merchant stage.Subsequently, during the buyer stage of a transaction the buyerinteracts with one or more interfaces, such as to provide a signature,to provide information for receiving a receipt, and/or to provide otherbuyer information. Thus in some examples, the buyer stage of thetransaction serves to complete the transaction, and the merchant maysubsequently proceed with a new transaction for the next buyer.

In the example of FIG. 4, the example UI 206 includes a plurality ofitem representations 208, as discussed above. In some examples, eachitem representation 208 may include an image (not shown) of a respectiveitem and/or a text description of the respective item. Thus, in theillustrated example, item representations 208 are presented in theinterface for a plurality of items A-O. Accordingly, in the case thatthe display 142 is a touchscreen display, the merchant may tap on one ofthe item representations 208 to select the corresponding item. Selecteditems are listed in the selected items area 210, which may include thetext description of the selected item, an image of the selected item anda price of the selected item, as indicated at 402 and 404. The selecteditems area 210 may further include a transaction tax as indicated at 406and a transaction total as indicated at 408. The interface 206 mayinclude various other virtual controls 410, 412, and 414 for performingvarious other functions, such as changing settings of the merchantapplication, sending or receiving communications to and from the serviceprovider, adding or removing items from the UI 206, and so forth.

As discussed above, in response to an indication of a preference fromthe merchant or a particular employee of the merchant, the UI 206 may bepresented in a selected first language indicated to be preferred by theparticular current user of the merchant device. Accordingly, thedescriptions of each item in the item representations 208 and in theselected items area 210 may be presented in the first language. Further,if the merchant accesses other features of the merchant application suchas through the virtual controls 410-414, those UIs may also be presentedin the first language.

FIGS. 5A and 5B illustrate example UIs that may be presented to thebuyer to enable the buyer to complete the buyer stage of the transactionaccording to some implementations. In the example of FIG. 5A, a buyer UI502 may be presented on the display 142, and may include a transactiontotal 504, indicating a total amount to be paid for the transaction; asignature block 506, which may enable the buyer to sign or otherwiseauthorize the transaction; a “clear signature” virtual control 508,which may enable the buyer to reset the signature block 506; and a “donesigning” virtual control 510 which may enable the buyer to accept asignature entered into the signature block 506. Additionally, in somecases, the UI 502 may include other features, such as for enabling theuser to enter a tip amount, determine a total with the tip, view alisting of items being purchased and corresponding prices, and so forth.

In some examples, the UI 502 may be presented on the display 142 in thesecond language, such as prior to repositioning of the display 142 fromthe first orientation facing in the direction of the merchant to thesecond orientation facing in the direction of the buyer. In otherexamples, the UI 502 may be presented initially on the display 142 inthe first language associated with the merchant, and in response todetermining that the display 142 has been repositioned to the secondorientation, the merchant device may then present the UI 502 in thesecond language. Thus, by changing the orientation of the display 142from the first orientation to the second orientation the text in the UImay change from the first language to the second language. If thedisplay 142 were to be repositioned back to the first orientation, thetext in the UI 502 may be changed back to the first language.

FIG. 5B illustrates another example of a UI 512 that may be presented onthe display 142, such as in response to the buyer selecting the donesigning virtual control 510. The UI 512 includes an inquiry 514 askinghow on the buyer would like to receive a receipt for the transaction.The UI 512 further includes a plurality of virtual controls 516, 518,520 and 522 that provide the option for the buyer to receive the receiptvia e.g., text message, email, printed receipt, or no receipt,respectively. For example, if the buyer has previously provided an emailaddress for receiving a receipt in a past transaction, the email addressmay be presented in the virtual control 518 and the buyer may select a“send receipt” virtual control 524 to have the receipt sent to theselected email address. Alternatively, if the buyer has not previouslyprovided an email address or if the buyer would like to receive thereceipt at a different email address, the buyer may select the virtualcontrol 518 and a virtual keyboard (not shown in FIG. 5B) may bedisplayed to enable the buyer to enter an email address. Similarly, ifthe buyer would like to receive the receipt by text message, and thebuyer's telephone number, if previously provided, is presented in thevirtual control 516, the buyer may select a “send receipt” virtualcontrol 526 to have the receipt sent. As discussed above, while the UI512 is presented on the display 142, and the display 142 is oriented inthe direction of the buyer, the UI 512 may be presented in the secondlanguage indicated to be preferred by the buyer.

FIGS. 6A and 6B illustrate example UIs that may be presented to thebuyer during the buyer stage of the transaction according to someimplementations. In the example of FIG. 6A, following the receptionselection of a method of receiving and receipt as discussed above, thebuyer may be presented with a UI 602 that provides the buyer with athank you message 604. The thank you message604 may be presented in thesecond language indicated to be preferred by the buyer. Additionally, insome examples, one or more virtual controls 606 and 608 may be presentedin the UI 602 as well. For example, when the display is reoriented backto facing the merchant, the merchant may use these virtual controls suchas for canceling the transaction as indicated by virtual control 606 orstart a new transaction as indicated by virtual control 608. Asdiscussed below with respect to FIG. 7, in some examples, based on thecurrent orientation of the display, the virtual control 606 and 608 maybe disabled, or may not be presented until after the display has beenrepositioned back to the first orientation.

FIG. 6B illustrates an example UI 610 that may be presented to the buyeraccording to some implementations. For example, the UI 610 may bepresented by the merchant application 112 in response to receivinglanguage information from the service computing device indicating that apreferred language for the particular buyer has not yet been determined.For instance, as mentioned above, the merchant device may send buyeridentification information to the service computing device whichattempts to determine a preferred language for the particular buyerparticipating in the current transaction by referring to a buyer profilefor that buyer. If a preferred language not been associated with thebuyer profile, the service computing device may send back languageinformation indicating that there is no preferred language associatedwith the particular buyer. In response to receiving this information,the merchant device may present the UI 610 to the buyer prior topresenting any other UIs to the buyer, such as UIs 502 or 512 discussedabove. Additionally, as another example, the UI 610 may be presented tothe merchant, and the merchant may ask the buyer if the buyer would liketo select a preferred language.

In the illustrated example, the UI 610 includes an inquiry 612 askingthe buyer if the buyer would like to select a preferred language.Furthermore, the UI 610 may present a plurality of virtual controls614-620 that provide various languages that the buyer may select as apreferred language. Furthermore, the buyer may be able to swipe the UI610 upward to view additional possible selections for preferredlanguages. Accordingly, the buyer may tap on one of the virtual controlsto select a desired preferred language. Furthermore, if the buyer doesnot desire to select a preferred language, the buyer may tap on orotherwise select a “no” virtual control 622.

If the buyer does select a preferred language, the language module 140on the merchant device may use this information for determining theappropriate UIs to present to the merchant. Furthermore, the buyer'spreferred language may be communicated to the service computing device108. The service computing device 108 may receive the preferred languageand associate the preferred language with the corresponding particularbuyer profile.

FIG. 7 illustrates an example environment 700 in which the orientationof at least the display 142 of the merchant device 104 may be used tocontrol access to certain UIs or other features, such as settings of themerchant application 112 and/or the merchant device 104. In the exampleUI 602 discussed above with respect to FIG. 6A, following completion ofthe transaction by the buyer, the virtual control 606 for canceling atransaction and the virtual control 608 for starting a new transactionmay be presented on the display 142. For example, in order to provide aspeedy transition to the next transaction, it is desirable for themerchant to be able to quickly start a new transaction. However,typically it is not desirable for the buyer to be able to select thevirtual control 608 for starting a new transaction, or the virtualcontrol 606 for canceling transaction. For example, it would beundesirable for the buyer to have access to the item selection interface206 discussed above with respect to FIGS. 2 and 4, and/or other featuresof the merchant application and/or the merchant device, such as accessto device settings, access to application settings, access tocommunications, access to stored information, and so forth.

Accordingly, in some implementations herein, while the display 142 isoriented facing toward the buyer, the virtual control 606 and thevirtual control 608 may be disabled such that if the buyer attempts toselect either of these virtual controls, the attempt to select thesecontrols may be ignored by the merchant device 104. When the display 142is repositioned to facing the merchant direction, the virtual controls606 and 608 may be enabled, e.g., such that a touch input to the virtualcontrol 606 results in presentation of another UI for canceling atransaction (not shown), and a touch input to the virtual control 608results in presentation of the UI 206 for entering information for a newtransaction. Alternatively, as another example, the virtual controls 606and 608 may not be presented until the merchant device 104 detects thatthe display 142 has been repositioned back to the first orientationfacing the direction associated with the merchant.

In the example of FIG. 7, when the display 142 is positioned in thefirst orientation 144, user interfaces 702 for both the merchant and/orbuyer may be presented and interacted with on the display 142. In otherwords, the merchant is presumed to be able to make inputs to the bothtypes of UIs, and may have full access to the UIs and other featuresaccessible on the merchant device. When the display 142 is repositionedto the second orientation 146, user interfaces 704 configured for thebuyer only may be presented or interacted with on the display 142, andaccess is disabled to other UIs, such as those configured to be accessedby the merchant. Accordingly, the merchant application 112 may controlthe information presented on the display 142 and/or the level ofinteractivity with the information presented on the display 142 based onthe detected orientation of the display 142.

As one example, the merchant device 104 may present the item selectionUI 206 discussed above on the display 142 for enabling the merchant toenter information for a transaction, such as to select items that thebuyer 114 wants to purchase. When the merchant has completed entry ofinformation related to the transaction, and has, e.g., swiped thepayment card 126 of the buyer, the merchant device 104 may present abuyer UI, such as the UIs 502 and/or 512 discussed above with respect toFIGS. 5A and 5B, respectively. For instance, the buyer UIs may includeone or more virtual controls configured for the buyer to enterinformation, make selections, or otherwise perform actions towardcompletion of the transaction. The buyer 114 may interact with the oneor more buyer UI, as discussed above.

When the buyer 114 has completed interaction with the buyer UIs, themerchant device may present the UI 602 discussed above. However, as thedisplay 142 is still facing the buyer direction e.g., is positioned inthe second orientation 146, the virtual controls 606 and 608 are eithernot selectable, or are not presented at all. The display 142 may bereoriented back to the first orientation 144 to face the merchant 110.Based at least in part on the change in orientation of the display 142from the second orientation 146 back to the first orientation 144, themerchant device 104 may enable initiation of a new transaction by themerchant 110. Accordingly, when the display 142 is accessible to thebuyer, only the buyer UIs are presented, and the buyer is unable tointeract with or otherwise access the merchant UIs, and is therebyunable to initiate a new transaction, or perform other actions that areproperly performed only by the merchant. Subsequently, when the merchantapplication 112 detects that the display 142 has been returned to thefirst orientation 144, e.g., facing in the merchant direction, themerchant 110 is able to initiate a new transaction or perform otherfunctions on the merchant device 104 that buyers may be restricted fromperforming. Furthermore, while the example merchant device configurationof FIG. 7 has been used to discuss this aspect, the other merchantdevice configurations, such as those discussed above with respect toFIGS. 3A-3C, and/or other merchant device configurations may also beused.

FIGS. 8-10 are flow diagrams illustrating example processes according tosome implementations. The processes of FIGS. 8-10 below are illustratedas collections of blocks in logical flow diagrams, which represent asequence of operations, some or all of which can be implemented inhardware, software or a combination thereof. In the context of software,the blocks may represent computer-executable instructions stored on oneor more computer-readable media that, when executed by one or moreprocessors, program the processors to perform the recited operations.Generally, computer-executable instructions include routines, programs,objects, components, data structures and the like that performparticular functions or implement particular data types. The order inwhich the blocks are described should not be construed as a limitation.Any number of the described blocks can be combined in any order and/orin parallel to implement the process, or alternative processes, and notall of the blocks need be executed. For discussion purposes, theprocesses are described with reference to the environments,architectures and systems described in the examples herein, although theprocesses may be implemented in a wide variety of other environments,architectures and systems.

FIG. 8 is a flow diagram of an example process 800 for determining alanguage to associate with a buyer profile according to someimplementations. In some examples, the example process 800 of FIG. 8 maybe executed by the service computing device 108, or by other suitablecomputing devices.

At 802, the computing device may receive POS transaction informationfrom a merchant device associated with a merchant. For example, asdiscussed above with respect to FIG. 1, the merchant device may sendtransaction information for a current transaction to the servicecomputing device. The transaction information may include buyeridentifying information and item information.

At 804, the computing device may compare the buyer identifyinginformation across multiple buyer profiles to determine a matching buyerprofile. For example, the buyer identifying information, such as paymentcard information, electronic payment account information, a buyer phonenumber, or other buyer identifying information, may be compared withbuyer identifying information contained in a plurality of buyer profilesto locate a particular buyer profile that corresponds to buyerinformation from the current transaction.

At 806, the computing device may determine whether a preferred languagehas been associated with the particular buyer profile associated withthe buyer participating in the current transaction.

At 808, if a preferred language has been associated with the particularbuyer profile, the computing device may send language information to themerchant device that indicates the preferred language of the buyerparticipating in the current transaction. For example, the languageinformation sent to the merchant device may at least identify thelanguage that has been associated with the particular buyer profile thatcorresponds to the buyer identifying information obtained for thecurrent transaction.

At 810, on the other hand, if the particular buyer profile does not havea preferred language associated with it, the computing device may send acommunication to the merchant device indicating that a preferredlanguage has not been determined for the buyer corresponding to theparticular buyer profile.

At 812, in some examples, the language information sent by the computingdevice may include an instruction that causes the merchant device topresent a user interface to the buyer that requests that the buyerindicate a preferred language. For example, as discussed above withrespect to FIG. 6B, the merchant device may present, e.g., prior topresenting other buyer interfaces, a user interface that enables thebuyer to select a preferred language from a list of potential preferredlanguages.

At 814, the computing device may determine whether an indication of apreferred language for the particular buyer profile has been receivedfrom the merchant device.

At 816, when the buyer selects a preferred language from the buyerinterface, the computing device may receive the indication of thepreferred language of the buyer from the merchant device.

At 818, the computing device may associate the preferred language withthe corresponding particular buyer profile. For example, the computingdevice may relate (e.g., in the case of a relational database) orotherwise associate the preferred language with the particular buyerprofile.

At 820, on the other hand, if the buyer does not provide a preferredlanguage, then the computing device may attempt to determine implicitlya preferred language of the buyer. As one example, if the buyer electsto receive receipts through an email address, when the buyer accesses areceipt using a browser, the language setting of the browser mayindicate a preferred language of the buyer. As another example, thebuyer profile associated with the buyer may include social networkinformation or other information that may be used to implicitlydetermine a preferred language of the buyer.

At 822, if a preferred language of the buyer is determined within athreshold confidence level, the process may proceed to block 818 toassociate the preferred language with the particular buyer profile. Onthe other hand, if the preferred language cannot be determined withinthe threshold confidence level, then a preferred language is notassociated with the particular buyer profile.

FIG. 9 is a flow diagram illustrating an example process 900 forpresenting information in multiple languages according to someimplementations. In some examples, the process 900 may be executed bythe merchant device 104, or by another suitable computing device.

At 902, the merchant device may present a first user interface in afirst language on a display associated with the merchant device.

At 904, the merchant device may receive, via the first UI, a merchantinput for a selection of at least one item for a POS transaction.

At 906, the merchant device may send, to a service computing device,during the POS transaction, buyer identifying information of the buyerparticipating in the POS transaction. For example, the merchant devicemay obtain the buyer identifying information from at least one of apayment card presented by the buyer, an electronic payment accountassociated with the buyer, a merchant incentive program that the buyerparticipates in, or other buyer identifying information, such as a phonenumber, email address, or the like, provided by the buyer.

At 908, the merchant device may receive, from the service computingdevice, an indication of a second language associated with the currentbuyer. For example, the second language may be different from the firstlanguage, and may have been previously associated with the buyer profilecorresponding to the buyer currently participating in the POStransaction.

At 910, the merchant device may detect positioning of the display from afirst orientation to a second orientation. For example, in the firstorientation, the screen of the display may face in the directionassociated with the merchant, such that the display may be viewable bythe merchant, but not easily viewable by the buyer. In the secondorientation, the screen of the display may be positioned to face in adirection that is associated with the buyer, such that the display maybe viewable by the buyer. In some examples, the merchant device mayinclude one or more sensors able to detect the orientation of thedisplay. Examples of the sensors may include a switch that is able todetect movement from the first orientation to the second orientation, anaccelerometer, a gyroscope, a compass, a proximity sensor, a switch, acamera, a microphone, a biometric sensor, or various other suitablesensors.

At 912, in response to detecting the display has been positioned in thesecond orientation, the merchant device may present a second UI on thedisplay in the second language. In some examples, the text of the secondUI may have been presented on the display in the first language prior tomovement of the display to the second orientation, which results in thetext of the UI being presented in the second language. In otherexamples, the second UI may not be presented on the display until afterthe display is moved to the second orientation.

At 914, in response to detecting the display has been positioned back tothe first orientation, the merchant device may present at least one ofthe second UI or a third UI in the first language. Accordingly, thedisplay may be flipped or otherwise repositioned between a firstorientation and a second orientation such that in the first orientationinformation is presented in the first language and in the secondorientation, information is presented in the second language during thetransaction with the particular buyer. When a subsequent transaction isconducted with a next buyer, a third language preferred by the nextbuyer, which may be different from the second language or the firstlanguage, may be used to present the information on the display when thedisplay is in the second orientation.

FIG. 10 is a flow diagram illustrating an example process 1000 forcontrolling access based on display orientation according to someimplementations. In some examples, the process may be executed by themerchant device or by another suitable computing device.

At 1002, the merchant device may present a first UI on a display of amerchant device. For example, the first UI may enable the merchant toselect one or more items that the buyer desires to purchase from themerchant.

At 1004, the merchant device may receive, via the first UI, a merchantinput for selection of at least one item for a POS transaction during amerchant stage of the POS transaction.

At 1006, based at least in part on the selection of the at least oneitem, the merchant device may present, on the display, a second UIconfigured to receive at least one buyer input. For example, followingentry of the item selection information by the merchant, the merchantmay swipe the payment card or may otherwise receive a payment instrumentfrom the buyer. In response, the merchant device may present a buyer UIconfigured to receive buyer interaction to enable the buyer to completethe buyer stage of the transaction.

At 1008, the merchant device may detect that the display has beenpositioned from a first orientation to a second orientation. Forexample, in the first orientation, the display may face in the directionassociated with the merchant such that the display may be viewable bythe merchant, but not easily viewable by the buyer. In the secondorientation, the display may be positioned to face in a direction thatis associated with the buyer, such that the display may be viewable bythe buyer. In some examples, the merchant device may include one or moresensors able to detect the orientation of the display. Examples of thesensors may include a switch that is able to detect movement from thefirst orientation to the second orientation, the accelerometer,gyroscope, a compass, a proximity sensor, a switch, a camera, amicrophone, a biometric sensor, or various other suitable sensors.Furthermore, in some examples, the second UI may be presented on thedisplay before the display is positioned in the second orientation,while in other examples, the second UI may be presented on the displayin response to detecting that the display has been positioned in thesecond orientation.

At 1010, the merchant device may receive at least one buyer touch inputto the second UI. For example, the buyer may provide a signature, mayprovide input for how to receive a receipt, may provide input to agreeto payment of an amount of the transaction, may enter an amount for agratuity, or may provide various other inputs during a buyer stage ofthe POS transaction.

At 1012, the merchant device may detect positioning of the display fromthe second orientation back to the first orientation. As discussedabove, one or more sensors may provide orientation information to themerchant device to enable the merchant device to determine that thedisplay is in the first orientation e.g., facing a direction associatedwith the merchant.

At 1014, in response to determining that the display has been positionedback to the first orientation, the merchant device may enabletouch-based initiation of a new transaction. For example, while thedisplay is positioned in the second orientation, initiation of a newtransaction may be prevented or otherwise disabled so as to prevent thebuyer from initiating a new transaction and/or from initiatingcancellation of the current transaction. As one example, virtualcontrols for initiating a new transaction and/or for canceling thecurrent transaction may be disabled so long as the display is positionedin the second orientation. As another example, the virtual controls forinitiating a new transaction and for canceling the current transactionmay not be presented on the display until the merchant device determinesthat the display has been moved back to the first orientation.

At 1016, while the display is positioned in the first orientation, themerchant device may receive, via a third UI, a touch input to initiate anew transaction. For example, the third UI may comprise the virtualcontrol for initiating a new transaction that is in disabled when thedisplay is in the second orientation, but which is enabled when thedisplay is positioned in the first orientation. Alternatively, asmentioned above, in some examples, the third UI may not be presenteduntil the merchant device has determined that the display is in thefirst orientation. In either alternative, in response to receiving thetouch input to initiate the new transaction, the merchant device maypresent the first UI on the display to enable the merchant to enter iteminformation for the new transaction. As another example, upon detectingthat the display has been reoriented to the first orientation, themerchant application may automatically present the first UI, e.g., UI206, to enable the merchant to begin entering information for a newtransaction.

The example processes described herein are only examples of processesprovided for discussion purposes. Numerous other variations will beapparent to those of skill in the art in light of the disclosure herein.Further, while the disclosure herein sets forth several examples ofsuitable frameworks, architectures and environments for executing theprocesses, implementations herein are not limited to the particularexamples shown and discussed. Furthermore, this disclosure providesvarious example implementations, as described and as illustrated in thedrawings. However, this disclosure is not limited to the implementationsdescribed and illustrated herein, but can extend to otherimplementations, as would be known or as would become known to thoseskilled in the art.

FIG. 11 illustrates an example architecture of a payment and languageinformation system 1100 able to provide a payment and languageinformation service according to some implementations. In the example ofFIG. 11, the service computing device 108 of the service provider 102includes a payment processing module 1102, which may be executed toprovide the payment and transaction functionality. The paymentprocessing module 1102 may receive at least transaction information 124for processing payments made through the buyer application 120 and/orthe merchant application 112. For example, the payment processing module1102 may receive transaction information 124, such as an amount of a POStransaction 1104, and may verify that the linked payment card can beused to pay for the transaction, such as by contacting a cardclearinghouse computing device or other bank computing device, asdiscussed additionally below. Furthermore, in some examples, the paymentprocessing module 1102 may redirect payment information for transactionsto be made using a payment card to a bank computing device 1106, whilein other examples, the merchant devices 104 may communicate directlywith an appropriate bank computing device 1106 or card payment networkcomputing device 1108 for approving or denying a transaction using aparticular payment card for a particular POS transaction 1104. Thepayment processing module 1102 and corresponding payment functionalitymay be implemented as one or more computer programs, or other executableinstructions, on the service computing device 108 in one or morelocations, such as for providing the payment systems, components, andtechniques described herein.

The example of FIG. 11 illustrates that one or more buyers 114 may haveone or more respective buyer devices 118 in some examples, which areable to communicate with at least one merchant device 104 and/or theservice computing device 108 over the one or more networks 106. Thebuyer device 118 may include the buyer application 120, as previouslydiscussed herein, which may include an electronic payment 214 thatprovides functionality for enabling the buyer 114 to make electronicpayments using the buyer device 118. In some examples, the buyerapplication 120 may include various other applications or modules, suchas for a buyer dashboard to enable the buyer to control information inthe buyer's profile, set buyer preferences, and so forth.

Further, the merchant device 104 may be associated with a merchant 110that participates in the payment service provided by the serviceprovider 102, and the merchant device 104 may include the merchantapplication 112. As discussed elsewhere herein, the buyer device 118 andthe merchant device 104 can each be a computing device able tocommunicate with each other, with the service computing device 108, andwith various other computing devices, through any suitable communicationprotocols, interfaces, and networks, including the one or morecommunication networks 106.

The buyer device 118 and the merchant device 104 can each include one ormore components, e.g., software or hardware, that are configured torespectively determine a geographic location of the buyer device 118and/or the merchant device 104, using, for example, various geolocationtechniques, e.g., a global positioning system (GPS), cell towerlocation, wireless access point location, wireless beacon location, andso forth. Further, the buyer device 118 and the merchant device 104 caneach be any appropriate device operable to send and receive requests,messages, or other types of information over the one or more networks106 or directly to each other. Some examples of buyer devices 118 andmerchant devices 104 are enumerated below. Additionally, while only asingle buyer device 118 and a single merchant device 104 are illustratedin the example of FIG. 11, in some implementations, there may bethousands, hundreds of thousands, or more, of the buyer devices 118 andthe merchant devices 104.

The one or more networks 106 can include any appropriate network,including a wide area network, such as the Internet; a local areanetwork, such an intranet; a wireless network, such as a cellularnetwork, a local wireless network, such as Wi-Fi and/or close-rangewireless communications, such as Bluetooth® and Bluetooth® low energy; awired network; or any other such network, or any combination thereof.Accordingly, the one or more networks 106 may include both wired and/orwireless communication technologies, including Bluetooth®, Bluetooth®low energy, Wi-Fi and cellular communication technologies, as well aswired or fiber optic technologies. Components used for suchcommunications can depend at least in part upon the type of network, theenvironment selected, or both. Protocols for communicating over suchnetworks are well known and will not be discussed herein in detail.Accordingly, the service computing device 108, the merchant devices 104,the buyer devices 118, and the other computing devices discussed hereinare able to communicate over the one or more networks 106 using wired orwireless connections, and combinations thereof.

Additionally, in some examples, transaction information may also beobtained with respect to buyers 114 that do not have a buyer device 118,the buyer application 120, and/or an account with the payment serviceprovided through the service computing device 108. The transactioninformation collected with respect to these buyers 114 may be sent tothe service computing device 108, and buyer profiles may be created forthe buyers 114. Should one or more of these buyers later sign up for theelectronic payment service, the transaction information of an existingbuyer profile for that buyer may be merged with the newly createdprofile.

In some implementations, the payment service enables card-less payments,e.g., electronic payments, for transactions between the buyers 114 andthe merchants 110 based on interaction of the buyer 114 with the buyerapplication 120 and interaction of the merchant 110 with the merchantapplication 112. Accordingly, in some examples, a card-less paymenttransaction may include a transaction conducted between a buyer 114 anda merchant 110 at a POS location during which an electronic paymentaccount of the buyer 114 is charged without the buyer 114 having tophysically present a payment card to the merchant 110 at the POSlocation. Consequently, the merchant 110 need not receive any detailsabout the financial account of the buyer 114 for the transaction to beprocessed. As one example, the electronic payment may be charged to acredit card issuer or credit card number that the buyer 114 providedwhen signing up with the service provider for the electronic paymentaccount. As another example, the buyer 114 may have a quantity of moneypre-paid in an account maintained for use in making the electronicpayments. Other variations will also be apparent to those of skill inthe art having the benefit of the disclosure herein.

Before conducting an electronic payment transaction, the buyer 114typically creates a user account with service provider of the paymentservice. The buyer 114 can create the user account, for example, byinteracting with the buyer application 120 that is configured to performelectronic payment transactions and that may execute on the buyer device118. When creating a buyer electronic payment account with the paymentservice, the buyer 114 may provide an image including the face of thebuyer, data describing a financial account of the buyer 114, e.g., acredit card number, expiration date, and a billing address. This userinformation can be securely stored by the payment service, such as in asecure database. Further, the buyer profiles 134 may be created for eachbuyer 114, which may include information about the buyer andtransactions conducted by the buyer.

The service computing device 108 may further include an analysis module1110. For example, the analysis module 1110 may receive the transactioninformation 124 and associate the transaction information 124 withappropriate merchant profiles 130 and appropriate buyer profiles 134.Thus, the analysis module 1110 may compare received transactioninformation 124, such as an identifier of the merchant device 104 or anidentifier of an instance of a merchant application 112 from which thetransaction information 124 is received for associating the transactioninformation 124 with a particular merchant profile 130. Furthermore, theanalysis module 1110 may extract buyer information such as a credit cardidentifier, buyer name, buyer email address, and various other pieces ofbuyer identifying information from the transaction information 124, andmay match this information with an existing buyer profile 134 or, if nomatch is found, then a new buyer profile 134 may be created.

The buyer profiles 134 and/or merchant profiles 130 described herein maybe created and maintained using any suitable types of data structures,and using any suitable data storage or database techniques. In someexamples, the transaction information and other profile information maybe maintained in a relational database in which pieces of informationfor individual buyer profiles may be stored distinctly from one another,but are related to or otherwise associated with each other in therelational database. For instance, a particular buyer profile 134 may beobtained by generating a view of a portion the data related in thedatabase to the particular buyer profile, or by otherwise extracting thedata from the database. Alternatively, of course, other types of storagetechniques may be used for generating and maintaining the buyer profiles134 and/or the merchant profiles 130. Furthermore, in some examples aprobabilistic model may be used to determine within a threshold level ofconfidence that transaction information 124 from a particulartransaction should be associated with a particular buyer profile 134.The analysis module 1110 may be configured to harmonize the transactioninformation that is received from various merchant devices so thatorphan or otherwise disconnected sets of transaction information thatcorrespond to different financial payment accounts, e.g., differentpayment cards or electronic payment accounts, etc., can be matched to orotherwise associated with particular buyer profiles. The analysis module1110 can generate the probabilistic model, for example, by utilizing oneor more of a weighted graph model, a probabilistic data store and/or atrained statistical model.

To accept be able to electronic payments for POS transactions 1104, themerchant 110 typically creates a merchant account with the paymentservice by providing information describing the merchant including, forexample, a merchant name, contact information, e.g., telephone numbers,the merchant's geographic location address, and one or more financialaccounts to which funds collected from buyers will be deposited. Thismerchant information can be securely stored by the payment service, forexample, in the merchant information 128, such as in a secure database.Further, a merchant profile 130 may be created for each merchant, whichmay include information about the merchant and transactions conducted bythe merchant.

The payment service can include one or more servers that are configuredto perform securely electronic financial transactions, e.g., electronicpayments for transactions between a buyer and a merchant, for example,through data communicated between the buyer device 118 and the merchantdevice 104.

Generally, when a buyer and a merchant enter into an electronic paymenttransaction, the transaction is processed by electronically transferringfunds from a financial account associated with the buyer account to afinancial account associated with the merchant account.

Determining whether the buyer device 118 is within a thresholdgeographic distance of the merchant device 104 can be accomplished indifferent ways including, for example, determining whether the buyerdevice 118 is within a threshold geographic radius of the merchantdevice 104, determining whether the buyer device 118 is within aparticular geofence, or determining whether the buyer device 118 cancommunicate with the merchant device 104 using a specified wirelesstechnology, e.g., Bluetooth® or Bluetooth® low energy (BLE). In someexamples, the payment service restricts electronic payment transactionsbetween the buyer 114 and the merchant 110 to situations where thegeographic location of the buyer device 118 is within a thresholdgeographic distance from a geographic location of the merchant device104.

The payment service can also be configured to communicate with the oneor more computing devices 1008 of a card payment network (e.g.,MasterCard®, VISA®) over the one or more networks 106 to conductfinancial transactions electronically. The payment service can alsocommunicate with one or more bank computing devices 1106 of one or morebanks over the one or more networks 106. For example, the paymentservice may communicate with an acquiring bank, and/or an issuing bank,and/or a bank maintaining buyer accounts for electronic payments.

The buyer 114 operating the buyer device 118 that is within a thresholdgeographic distance of the merchant device 104 can interact with thebuyer application 120 executed on the buyer device 118 to conduct anelectronic payment transaction with the merchant 110. While interactingwith the buyer application 120, the buyer 114 can select the merchant110, from a listing of merchants 110, with whom the buyer 114 wants toenter into an electronic payment transaction. The buyer 114 can selectthe merchant 110, for example, by selecting a “check in” optionassociated with the merchant 110. The buyer device 118 can communicatedata to the payment service indicating that the buyer 114 has checked inwith the merchant 110. In response, the payment service can communicatedata to notify the merchant device 104 that the buyer has checked in.The merchant application 112 executing on the merchant device 104 cannotify the merchant 110 that the buyer has electronically checked inwith the merchant 110 through a display screen of the merchant device104.

After checking in, the buyer 114 can obtain, or request, items that areavailable to be acquired from the merchant 110. When the buyer 114 isready to enter into the card-less payment transaction, the buyer 114can, for example, approach a point of sale for the merchant 110 andidentify him or herself. For example, the buyer 114 can verbally notifythe merchant 110 that the buyer 114 wants to enter into a card-lesspayment transaction and can provide the merchant 110 with the buyer'sname. The merchant 110 can then interact with the merchant application112 to select the buyer 114, from a listing of buyers that have checkedin with the merchant 110, to initiate an electronic payment transactionfor the item(s) being acquired by the buyer 114.

The payment service can then communicate with the computing device 1108of a card payment network to complete an electronic payment transactionfor the total amount to be charged to the buyer's electronic paymentaccount. When the electronic payment transaction is complete, thepayment service can communicate data describing the electronic paymentfor the transaction to the buyer device 118, e.g., as an electronicreceipt 1112, which can, for example, notify the buyer 114 of the totalamount charged to the buyer for the electronic payment for thetransaction with the particular merchant. At least a portion of areceipt 1112, such as an image accessible through an image tag, may bestored by the service computing device 108. As discussed above, theservice computing device 108 may detect a language associated with abuyer browser that accesses the receipts 1112, such as for determiningimplicitly a language preferred by the particular buyer. Further, whilea mobile buyer device 118 is described in this example for purposes ofexplanation, additional or alternative types of devices may be used inother examples.

In addition, in some examples, the service provider 102 may makeavailable one or more service provider websites 1114 that enablemerchants 110 to advertise items on the service provider website(s). Forexample, merchants 110 may offer 114 on the website. The buyers maypurchase the items using a web browser, or other application on acomputing device, such as the buyer device 118 or other computingdevice. The transaction information from these transactions may beprovided to the service computing device 108 to add further to thetransaction information in the buyer profiles 134 and the merchantprofiles 130.

In addition, the analysis module 1110 and/or the language determinationmodule 136 may access other websites 1116 when determining informationabout buyers, respectively. For example, demographic information andother buyer information may be obtained from the US Census Bureauwebsite, social network sites, a microblog site, or other onlinepresences of the various different buyers. Similarly, geographicinformation may be obtained from websites that provide maps and othergeographic or demographic information, or the like.

FIG. 12 illustrates select example components of an example merchantdevice 104 according to some implementations. The merchant device 104may be any suitable type of computing device, e.g., portable,semi-portable, semi-stationary, or stationary. Some examples of themerchant device 104 may include tablet computing devices; smart phonesand mobile communication devices; laptops, netbooks and other portablecomputers or semi-portable computers; desktop computing devices,terminal computing devices and other semi-stationary or stationarycomputing devices; dedicated register devices; wearable computingdevices, or other body-mounted computing devices; augmented realitydevices; or other computing devices capable of sending communicationsand performing the functions according to the techniques describedherein.

In the illustrated example, the merchant device 104 includes at leastone processor 1202, one or more computer-readable media 1204, one ormore communication interfaces 1206, and one or more input/output (I/O)devices 1208. Each processor 1202 may itself comprise one or moreprocessors or processing cores. For example, the processor 1202 can beimplemented as one or more microprocessors, microcomputers,microcontrollers, digital signal processors, central processing units,state machines, logic circuitries, and/or any devices that manipulatesignals based on operational instructions. In some cases, the processor1202 may be one or more hardware processors and/or logic circuits of anysuitable type specifically programmed or configured to execute thealgorithms and processes described herein. The processor 1202 can beconfigured to fetch and execute computer-readable processor-executableinstructions stored in the computer-readable media 1204.

Depending on the configuration of the merchant device 104, thecomputer-readable media 1204 may be an example of tangiblenon-transitory computer storage media and may include volatile andnonvolatile memory and/or removable and non-removable media implementedin any type of technology for storage of information such ascomputer-readable processor-executable instructions, data structures,program modules or other data. The computer-readable media 1204 mayinclude, but is not limited to, RAM, ROM, EEPROM, flash memory,solid-state storage, magnetic disk storage, optical storage, and/orother computer-readable media technology. Further, in some cases, themerchant device 104 may access external storage, such as RAID storagesystems, storage arrays, network attached storage, storage areanetworks, cloud storage, or any other medium that can be used to storeinformation and that can be accessed by the processor 1202 directly orthrough another computing device or network. Accordingly, thecomputer-readable media 1204 may be computer storage media able to storeinstructions, modules or components that may be executed by theprocessor 1202. Further, when mentioned, non-transitorycomputer-readable media exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

The computer-readable media 1204 may be used to store and maintain anynumber of functional components that are executable by the processor1202. In some implementations, these functional components compriseinstructions or programs that are executable by the processor 1202 andthat, when executed, implement operational logic for performing theactions and services attributed above to the merchant device 104.Functional components of the merchant device 104 stored in thecomputer-readable media 1204 may include the merchant application 112.In this example, the merchant application 112 includes the languagemodule 140, discussed above, a transaction module 1210 and a dashboardmodule 1212. For example, the transaction module 1210 may presentvarious user interfaces, as discussed above, to enable the merchant toconduct transactions, receive payments, and so forth, as well as forcommunicating with the service computing device 108 for processingpayments and sending transaction information. Further, the dashboardmodule 1212 may enable the merchant to manage the merchant's account,the merchant profile, merchant preferences, view item pricinginformation, and the like. Additional functional components may includean operating system 1214 for controlling and managing various functionsof the merchant device 104 and for enabling basic user interactions withthe merchant device 104.

In addition, the computer-readable media 1204 may also store data, datastructures and the like, that are used by the functional components. Forexample, data stored by the computer-readable media 1204 may includeitem information 1216 that includes information about the items offeredby the merchant, which may include a list of items currently availablefrom the merchant, images of the items, descriptions of the items,prices of the items, and so forth. For instance, when the merchant 110is setting up the merchant application 112 to accept payments forparticular items offered by the merchant 110, the merchant may enter theitem information 1216 for the particular items. Depending on the type ofthe merchant device 104, the computer-readable media 1204 may alsooptionally include other functional components and data, such as othermodules and data 1218, which may include programs, drivers, etc., andthe data used or generated by the functional components. Further, themerchant device 104 may include many other logical, programmatic andphysical components, of which those described are merely examples thatare related to the discussion herein.

The communication interface(s) 1206 may include one or more interfacesand hardware components for enabling communication with various otherdevices, such as over the network(s) 106 or directly. For example,communication interface(s) 1206 may enable communication through one ormore of the Internet, cable networks, cellular networks, wirelessnetworks (e.g., Wi-Fi) and wired networks, as well as close-rangecommunications such as Bluetooth®, Bluetooth® low energy, and the like,as additionally enumerated elsewhere herein.

FIG. 12 further illustrates that the merchant device 104 may include thedisplay 142 mentioned above. Depending on the type of computing deviceused as the merchant device 104, the display 142 may employ any suitabledisplay technology. For example, the display 142 may be a liquid crystaldisplay, a plasma display, a light emitting diode display, an OLED(organic light-emitting diode) display, an electronic paper display, orany other suitable type of display able to present digital contentthereon. In some examples, the display 142 may have a touch sensorassociated with the display 142 to provide a touchscreen displayconfigured to receive touch inputs for enabling interaction with agraphic interface presented on the display 142. Accordingly,implementations herein are not limited to any particular displaytechnology. Alternatively, in some examples, the merchant device 104 maynot include the display 142, and information may be presented by othermeans, such as aurally.

The merchant device 104 may further include the one or more I/O devices1208. The I/O devices 1208 may include speakers, a microphone, a camera,and various user controls (e.g., buttons, a joystick, a keyboard, akeypad, etc.), a haptic output device, and so forth.

In addition, the merchant device 104 may include or may be connectableto a card reader 1220. In some examples, the card reader may plug in toa port in the merchant device, such as a microphone/headphone port, adata port, or other suitable port. The card reader may include a readhead for reading a magnetic strip of a payment card, and further mayinclude encryption technology for encrypting the information read fromthe magnetic strip. Alternatively, numerous other types of card readersmay be employed with the merchant devices 104 herein, depending on thetype and configuration of the merchant device 104.

Other components included in the merchant device 104 may include varioustypes of sensors, which may include a GPS device 1222 able to indicatelocation information. Further, the merchant device may include one ormore sensors 1224, such as an accelerometer, gyroscope, compass,proximity sensor, camera, microphone, and/or a switch, as discussedabove. Additionally, the merchant device 104 may include various othercomponents that are not shown, examples of which include removablestorage, a power source, such as a battery and power control unit, andso forth.

In addition, the merchant device 104 may include various externalcomponents or peripherals such as the support 148 or the other supportsdiscussed herein. As mentioned above, in some examples the support mayinclude one or more sensors 1226 such as a switch, an accelerometer, acompass, a gyroscope, a proximity sensor, a camera, a microphone, orother suitable sensors for determining the orientation of the merchantdevice. Furthermore, in some examples of the merchant device 104 mayinclude a cash drawer 1228, a printer 1230, such as for printingreceipts, and/or a barcode reader 1232 for scanning items to bepurchased. Furthermore, the merchant device 104 may be connected to, orable to connect to, various external devices 1234 such as othercomputing devices and or external storage devices.

FIG. 13 illustrates select components of the service computing device108 that may be used to implement some functionality of the paymentservice described herein. The service computing device 108 may beoperated by a service provider that provides the payment service, andmay include one or more servers or other types of computing devices thatmay be embodied in any number of ways. For instance, in the case of aserver, the modules, other functional components, and data may beimplemented on a single server, a cluster of servers, a server farm ordata center, a cloud-hosted computing service, a cloud-hosted storageservice, and so forth, although other computer architectures mayadditionally or alternatively be used.

Further, while the figures illustrate the components and data of theservice computing device 108 as being present in a single location,these components and data may alternatively be distributed acrossdifferent computing devices and different locations in any manner.Consequently, the functions may be implemented by one or more servicecomputing devices, with the various functionality described abovedistributed in various ways across the different computing devices.Multiple service computing devices 108 may be located together orseparately, and organized, for example, as virtual servers, server banksand/or server farms. The described functionality may be provided by theservers of a single entity or enterprise, or may be provided by theservers and/or services of multiple different buyers or enterprises.

In the illustrated example, each service computing device 108 mayinclude one or more processors 1302, one or more computer-readable media1304, and one or more communication interfaces 1306. Each processor 1302may be a single processing unit or a number of processing units, and mayinclude single or multiple computing units or multiple processing cores.The processor(s) 1302 can be implemented as one or more microprocessors,microcomputers, microcontrollers, digital signal processors, centralprocessing units, state machines, logic circuitries, and/or any devicesthat manipulate signals based on operational instructions. For instance,the processor(s) 1302 may be one or more hardware processors and/orlogic circuits of any suitable type specifically programmed orconfigured to execute the algorithms and processes described herein. Theprocessor(s) 1302 can be configured to fetch and executecomputer-readable instructions stored in the computer-readable media1304, which can program the processor(s) 1302 to perform the functionsdescribed herein.

The computer-readable media 1304 may include volatile and nonvolatilememory and/or removable and non-removable media implemented in any typeof technology for storage of information, such as computer-readableinstructions, data structures, program modules, or other data. Suchcomputer-readable media 1304 may include, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, optical storage,solid state storage, magnetic tape, magnetic disk storage, RAID storagesystems, storage arrays, network attached storage, storage areanetworks, cloud storage, or any other medium that can be used to storethe desired information and that can be accessed by a computing device.Depending on the configuration of the service computing device 108, thecomputer-readable media 1304 may be a type of computer-readable storagemedia and/or may be a tangible non-transitory media to the extent thatwhen mentioned, non-transitory computer-readable media exclude mediasuch as energy, carrier signals, electromagnetic waves, and signals perse.

The computer-readable media 1304 may be used to store any number offunctional components that are executable by the processors 1302. Inmany implementations, these functional components comprise instructionsor programs that are executable by the processors 1302 and that, whenexecuted, specifically configure the one or more processors 1302 toperform the actions attributed above to the service computing device108. Functional components stored in the computer-readable media 1304may include the language determination module 136, the analysis module1110, and the payment processing module 1102. Additional functionalcomponents stored in the computer-readable media 1304 may include anoperating system 1308 for controlling and managing various functions ofthe service computing device 108.

In addition, the computer-readable media 1304 may store data used forperforming the operations described herein. Thus, the computer-readablemedia may store the merchant information 128, including the merchantprofiles 130, and the buyer information 132, including the buyerprofiles 134. The service computing device 108 may also include ormaintain other functional components and data, such as other modules anddata 1310, which may include programs, drivers, etc., and the data usedor generated by the functional components. Further, the servicecomputing device 108 may include many other logical, programmatic andphysical components, of which those described above are merely examplesthat are related to the discussion herein.

The communication interface(s) 1306 may include one or more interfacesand hardware components for enabling communication with various otherdevices, such as over the network(s) 106. For example, communicationinterface(s) 1306 may enable communication through one or more of theInternet, cable networks, cellular networks, wireless networks (e.g.,Wi-Fi) and wired networks, as well as close-range communications such asBluetooth®, Bluetooth® low energy, and the like, as additionallyenumerated elsewhere herein.

The service computing device 108 may further be equipped with variousinput/output (I/O) devices 1312. Such I/O devices 1312 may include adisplay, various user interface controls (e.g., buttons, joystick,keyboard, mouse, touch screen, etc.), audio speakers, connection portsand so forth.

FIG. 14 illustrates select example components of the buyer device 118that may implement the functionality described above according to someexamples. The buyer device 118 may be any of a number of different typesof portable computing devices. Some examples of the buyer device 118 mayinclude smart phones and mobile communication devices; tablet computingdevices; laptops, netbooks and other portable computers; wearablecomputing devices and/or body-mounted computing devices, which mayinclude watches and augmented reality devices, such as helmets, gogglesor glasses; and any other portable device capable of sendingcommunications and performing the functions according to the techniquesdescribed herein.

In the example of FIG. 14, the buyer device 118 includes components suchas at least one processor 1402, one or more computer-readable media1404, the one or more communication interfaces 1406, and one or moreinput/output (I/O) devices 1414. Each processor 1402 may itself compriseone or more processors or processing cores. For example, the processor1402 can be implemented as one or more microprocessors, microcomputers,microcontrollers, digital signal processors, central processing units,state machines, logic circuitries, and/or any devices that manipulatesignals based on operational instructions. In some cases, the processor1402 may be one or more hardware processors and/or logic circuits of anysuitable type specifically programmed or configured to execute thealgorithms and processes described herein. The processor 1402 can beconfigured to fetch and execute computer-readable processor-executableinstructions stored in the computer-readable media 1404.

Depending on the configuration of the buyer device 118, thecomputer-readable media 1404 may be an example of tangiblenon-transitory computer storage media and may include volatile andnonvolatile memory and/or removable and non-removable media implementedin any type of technology for storage of information such ascomputer-readable processor-executable instructions, data structures,program modules or other data. The computer-readable media 1404 mayinclude, but is not limited to, RAM, ROM, EEPROM, flash memory,solid-state storage, magnetic disk storage, optical storage, and/orother computer-readable media technology. Further, in some cases, thebuyer device 118 may access external storage, such as RAID storagesystems, storage arrays, network attached storage, storage areanetworks, cloud storage, or any other medium that can be used to storeinformation and that can be accessed by the processor 1402 directly orthrough another computing device or network. Accordingly, thecomputer-readable media 1404 may be computer storage media able to storeinstructions, modules or components that may be executed by theprocessor 1402. Further, when mentioned, non-transitorycomputer-readable media exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

The computer-readable media 1404 may be used to store and maintain anynumber of functional components that are executable by the processor1402. In some implementations, these functional components compriseinstructions or programs that are executable by the processor 1402 andthat, when executed, implement operational logic for performing theactions and services attributed above to the buyer device 118.Functional components of the buyer device 118 stored in thecomputer-readable media 1404 may include the buyer application 120, asdiscussed above. In this example, the buyer application 120 includes theelectronic payment module 214, as discussed above, and a buyer dashboardmodule 1410. For example, the buyer dashboard module 1410 may presentthe buyer with an interface for managing the buyer's account, changinginformation, changing preferences, and so forth. Additional functionalcomponents may include an operating system 1412 for controlling andmanaging various functions of the buyer device 118 and for enablingbasic user interactions with the buyer device 118.

In addition, the computer-readable media 1404 may also store data, datastructures and the like, that are used by the functional components.Depending on the type of the buyer device 118, the computer-readablemedia 1404 may also optionally include other functional components anddata, such as other modules and data 1406, which may includeapplications, programs, drivers, etc., and the data used or generated bythe functional components. Further, the buyer device 118 may includemany other logical, programmatic and physical components, of which thosedescribed are merely examples that are related to the discussion herein.

The communication interface(s) 1406 may include one or more interfacesand hardware components for enabling communication with various otherdevices, such as over the network(s) 106 or directly. For example,communication interface(s) 1406 may enable communication through one ormore of the Internet, cable networks, cellular networks, wirelessnetworks (e.g., Wi-Fi) and wired networks, as well as close-rangecommunications such as Bluetooth®, Bluetooth® low energy, and the like,as additionally enumerated elsewhere herein.

FIG. 14 further illustrates that the buyer device 118 may include adisplay 1416. Depending on the type of computing device used as thebuyer device 118, the display may employ any suitable displaytechnology. For example, the display 1416 may be a liquid crystaldisplay, a plasma display, a light emitting diode display, an OLED(organic light-emitting diode) display, an electronic paper display, orany other suitable type of display able to present digital contentthereon. In some examples, the display 1416 may have a touch sensorassociated with the display 1416 to provide a touchscreen displayconfigured to receive touch inputs for enabling interaction with agraphic interface presented on the display 1416. Accordingly,implementations herein are not limited to any particular displaytechnology. Alternatively, in some examples, the buyer device 118 maynot include a display.

The buyer device 118 may further include the one or more I/O devices1408. The I/O devices 1408 may include speakers, a microphone, a camera,and various user controls (e.g., buttons, a joystick, a keyboard, akeypad, etc.), a haptic output device, and so forth.

Other components included in the buyer device 118 may include varioustypes of sensors, which may include a GPS device 1418 able to indicatelocation information, as well as other sensors (not shown) such as anaccelerometer, gyroscope, compass, proximity sensor, and the like.Additionally, the buyer device 118 may include various other componentsthat are not shown, examples of which include removable storage, a powersource, such as a battery and power control unit, and so forth.

Various instructions, methods and techniques described herein may beconsidered in the general context of computer-executable instructions,such as program modules stored on computer-readable media, and executedby the processor(s) herein. Generally, program modules include routines,programs, objects, components, data structures, etc., for performingparticular tasks or implementing particular abstract data types. Theseprogram modules, and the like, may be executed as native code or may bedownloaded and executed, such as in a virtual machine or otherjust-in-time compilation execution environment. Typically, thefunctionality of the program modules may be combined or distributed asdesired in various implementations. An implementation of these modulesand techniques may be stored on computer storage media or transmittedacross some form of communication media.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as example forms ofimplementing the claims.

What is claimed is:
 1. A point-of-sale (POS) system used in atransaction between a merchant and a customer, the POS systemcomprising: a frame; a first terminal mounted to the frame using a firstconnection such that the first terminal is able to rotate about thefirst connection, the first terminal configured to support a firstdevice that is oriented in a merchant-facing direction, the first deviceconfigured to present a merchant graphical user interface (merchant GUI)on a first touchscreen display of the first device; a second terminalmounted to the frame using a second connection, the second terminalconfigured to support a second device that is oriented in acustomer-facing direction, the second device configured to present acustomer graphical user interface (GUI) on a second touchscreen displayof the second device, the second terminal in communication with thefirst terminal; a card reader oriented such that the card reader isaccessible by the customer, the card reader including a reading deviceconfigured to read information off a payment card used during thetransaction; three or more processors, wherein at least one of the threeor more processors controls the merchant GUI, and wherein at least oneof the three or more processors controls the customer GUI; and one ormore communication interfaces configured to send the information to apayment system.
 2. The POS system as recited in claim 1, wherein: theinformation comprises first information; the one or more communicationinterfaces are further configured to receive, from the payment system,second information associated with the customer; the first device isfurther configured to present, based at least in part on the secondinformation, third information associated with the transaction using themerchant GUI on the first touchscreen display; and the second device isfurther configured to present, based at least in part on the secondinformation, fourth information associated with the transaction usingthe customer GUI on the second touchscreen display.
 3. The POS system asrecited in claim 1, wherein the one or more communication devicescomprise at least one of a wireless fidelity transceiver, a GlobalPositioning System receiver, or a Bluetooth transceiver.
 4. The POSsystem as recited in claim 1, wherein the card reader comprises a firstcard reader, and wherein the POS system further comprises a second cardreader configured to read the information off the payment card.
 5. ThePOS system as recited in claim 1, wherein the card reader is mounted tothe frame such that the card reader is lower on the POS system than thesecond device.
 6. The POS system as recited in claim 1, wherein: thecard reader is further to encrypt the information; and the firstterminal is further configured to receive the information as encryptedfrom the card reader.
 7. The POS system as recited in claim 1, wherein:the first device is further configured to receive, using the firsttouchscreen display, first input indicating at least one item or servicebeing purchased by the customer; and the second device is furtherconfigured to receive, using the second touchscreen display, secondinput indicating information associated with the customer.
 8. The POSsystem as recited in claim 1, wherein: the merchant GUI includes firstinformation associated with the transaction, the first informationindicating at least one item or service being purchased by the customerduring the transaction; and the customer GUI includes at least onefeatures that enables the customer to enter second informationassociated with completing the transaction.
 9. A point-of-sale (POS)system used in a transaction between a merchant and a customer, the POSsystem comprising: a frame; a first touchscreen display mounted to theframe such that the first touchscreen display is orientated in amerchant-facing direction, wherein the first touchscreen display isrotatable about a connection of the frame; a second touchscreen displaymounted to the frame such that the second touchscreen display isoriented in a customer-facing direction; a card reader oriented suchthat the card reader is accessible by the customer, the card readerconfigured to receive information from a payment card used during thetransaction; one or more communication interfaces; three or moreprocessors; and one or more computer-readable media storing instructionsthat, when executed by at least one of the three or more processors,cause the at least one of the three or more processors to performoperations comprising: presenting a merchant graphical user interface(merchant GUI) using the first touchscreen display, the merchant GUIincluding first information associated with the transaction; presentinga customer graphical user interface (customer GUI) using the secondtouchscreen display, the customer GUI including second informationassociated with the transaction; receiving the information from the cardreader during the transaction; and sending, using the one or morecommunication interfaces, the information to a payment system.
 10. ThePOS system as recited in claim 9, the operations further comprisingreceiving, from the payment system, using the one or more communicationinterfaces, third information associated with the customer.
 11. The POSsystem as recited in claim 10, the operations further comprisingdetermining how to present the second information using the secondtouchscreen display based at least in part on the third informationassociated with the customer.
 12. The POS system as recited in claim 9,the operations further comprising: receiving, using the firsttouchscreen display, first input indicating at least one item or servicepurchased by the customer during the transaction; and receiving, usingthe second touchscreen display, second input indicating at least one ofa signature of the customer, an amount of a tip, contact informationassociated with the customer, or a language.
 13. The POS system asrecited in claim 9, further comprising at least one of a wirelessfidelity transceiver, a Global Positioning System receiver, or aBluetooth transceiver.
 14. The POS system as recited in claim 9, whereinthe card reader is mounted to the frame such that the card reader islower on the POS system than the second touchscreen display.
 15. Amethod of interacting between a first touchscreen device and a secondtouchscreen device of a point-of-sale (POS) system, the methodcomprising: presenting a merchant interface on the first touchscreendevice mounted to a frame, the first touchscreen device being orientedin a merchant-facing direction and configured to rotate about aconnection of the frame, where the first touchscreen is controlled by atleast a first processor; receiving, using the first touchscreen device,information associated with an item or service being purchased during atransaction; presenting a customer interface on the second touchscreendevice mounted to the frame, the second touchscreen device beingoriented in a customer-facing direction and being controlled by at leasta second processor; initiating a payment procedure using the firsttouchscreen device; presenting a payment total for the item or theservice using the customer interface on the second touchscreen device;receiving, using a card reader that is mounted on the frame andaccessible by a customer, payment information associated with a paymentcard, the card reader including at least a magnetic strip reading deviceconfigured to the payment information from the payment card during thetransaction; and sending the payment information to a payment system toobtain authorization for the transaction.
 16. The method as recited inclaim 15, wherein the information comprises first information, andwherein the method further comprises: receiving, from the paymentsystem, second information associated with the customer; determining howto present third information on the second touchscreen device using thesecond information, the third information including at least anindication of the item or the service; and presenting the thirdinformation using the customer interface on the second touchscreendevice.
 17. The method as recited in claim 16, further comprising:determining how to present fourth information on the first touchscreendevice using the second information; and presenting the fourthinformation using the merchant interface on the first touchscreendevice.
 18. The method as recited in claim 15, wherein the informationcomprises first information, and wherein the method further comprisesreceiving, using the second touchscreen display, input indicating secondinformation associated with the customer, the second informationincluding at least one of a signature of the customer, an amount of atip, contact information associated with the customer, or a language.19. The method as recited in claim 18, further comprising: determininghow to present third information on the second touchscreen device usingthe second information; and presenting the third information using thecustomer interface on the second touchscreen device.
 20. The method asrecited in claim 15, further comprising: receiving, from the paymentsystem, an indication that the payment card is authorized for thetransaction; and presenting, using the merchant interface on the firsttouchscreen device, additional information that indicates that thepayment card was authorized for the transaction